|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4145 (2005)
|
|
Title:
|
TCP-Based Media Transport in the Session Description Protocol (SDP).
|
|
|
2.
|
Status of approval:
|
|
|
Proposed Standard approved by the IETF IESG (September 2005).
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 4145 defines the "a=connection" and "a=setup" attributes that are used by the draft Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4145
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since September 2005. This text is a Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4145 was published in September, 2005. Updated by RFC 4572.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
see 8 below
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Postel, J., "Transmission Control Protocol", STD 7, RFC 793,/
September 1981./
/
[2] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet/
Mail Extensions (MIME) Part Four: Registration Procedures",/
BCP 13, RFC 2048, November 1996./
/
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[4] Handley, M. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[5] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
Session Description Protocol (SDP)", RFC 3264, June 2002./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
